home *** CD-ROM | disk | FTP | other *** search
- Path: darkstar.UCSC.EDU!dfong
- From: dfong@cse.ucsc.edu (Don Fong)
- Newsgroups: comp.lang.c++,comp.os.ms-windows.programmer.tools.owl
- Subject: Re: BC++ 5.0: send back or wait for patches?
- Date: 19 Apr 1996 22:22:05 GMT
- Organization: UC Santa Cruz CIS/CE
- Message-ID: <4l93md$5o2@darkstar.UCSC.EDU>
- References: <4l1lu7$jhb@head.globalcom.net> <4l8a9m$9qd@larry.rice.edu>
- NNTP-Posting-Host: arapaho.cse.ucsc.edu
-
- In article <4l8a9m$9qd@larry.rice.edu>,
- Karsten E. Braaten <karsten@landau.rice.edu> wrote:
- >Jeff French (jfrench@shentel.net) wrote:
- >> By the way, if things get to bad in the IDE, just create a
- >> MAKE file and build your apps using your favorite editor and
- >> the command line compilers...they are still available...just
- >> a thought.
- >
- > Does anybody know if Borland's make can handle lines longer than
- >128 characters yet? If not, make will quickly become a pain in the
- >arse with its 'response' files and all. Peace....
- the problem isn't with make itself; the 128 char limitation is
- a DOS limitation. in order to overcome it, the individual tools
- have to have some mechanism for passing a big argument list.
- the "response files" are one such mechanism, and make does provide
- pretty good support for it.
- i agree it's a pain in the ass. but make itself is not the problem.
-
- which reminds me - anyone care to share their "secrets of Borland
- make"? i think from reading the manual that it has some pretty
- powerful (although quirky) features. but the documentation alone
- is not sufficient to figure out how to use them. anyone else?
- like, has anyone gotten ".path.obj =" to work?
- what do those {}'s do in rules?
-
- or how about "mysterious bugs of Borland make"?
-
- --
- --- don fong ``i still want the peace dividend''
- --
-